Finding links between multiple projects
2021-05-04
An experiment to pick up keywords from the most recent one-day update in Scrapbox's Project A and present pages containing those keywords from Project B.
In this case, A is this public project and B is a private project of about 400 pages
If it seems to have a good effect, run it regularly once a day.
context
What we did.
Get ✅public's most recently updated pages
✅Extract keywords from its content
Just the one that is explicitly bracketed for now.
You can get it from the API.
✅Find and present ✅from different sources that contain those keywords.
There are two ways to search on your own after exporting to JSON or by hitting the search API.
This time, the search API
How to present
Create a page in private
Because the search results of a private project cannot be made public
There is an option to send a DM in Slack.
✅ this time I printed it and pasted it into Scrapbox by hand
result
(of) good appearance
I thought it was a private memo repository with not much information, but there were some surprisingly interesting pages.
I got some hits from the experiment, like the one where I transcribed a recording of a video conference.
105 keywords extracted from 24 hours of activity
The number of hits found in the search is 11.
The search API yields the hit rows.
There are some not-so-good keywords.
Research, Organization, Scrapbox, Unexplored Jr.
Too many hits.
It is better to display only the information "many hits" if the number of hits exceeds a certain level.
In the original project, it is only connected if both pages are bracketed, which is not a large number.
Three of the four cases were bracketed.
So, if you have a lot of search results, you can only show the number of results instead of the number of results, and bracket that search term instead.
Always do search keyword bracketing.
Rather, "Is there already a link?" and if so, is it better not to search?
impressions
relatively good
There are a number of other projects that seem to have a lot of interesting content dead in the water.
I want to have more than one target project.
additional experiment
I was thinking mainly of my public/private collaboration, so I couldn't publish the results because one of them was private.
I realized I could do both public.
And with the current version, which uses search instead of export, you can target other people's projects without any permission.
puppeteer
Puppeteer is a Node library which provides a high-level API to control headless Chrome or Chromium over
A Guide to Automating & Scraping the Web with JavaScript (Chrome + Puppeteer + Node JS)]
Puppeteer is a Node library which provides a high-level API to control headless Chrome or Chromium over
It can also be configured to use full (non-headless) Chrome or Chromium.
It is thought to be a headless Chrome that can be operated from the command line.
A Guide to Automating & Scraping the Web with JavaScript (Chrome + Puppeteer + Node JS)]
fbclid=IwAR3LXwnspP4W9R79YvAjlC760Q62f_kgBMVpUmRP9WmYok8_xWEMVLkjyZM]
gated community
A gated community is a residential area with a gate (gate) and a wall around the perimeter to restrict access to the property by non-residents, thereby preventing through traffic and improving security.
The concept of a gated community itself is not new; there have been concessions and U.S. military houses in the past, and it is merely a redefinition of the term. In Japan, it is also referred to as a gated town1 or gated community2. ` Updated to account for the case where the output project and the project to be searched are different.
The [1] in the quote from rushitamemo has become a search keyword.
Should it be ~? I fixed it by hand for now.
The output of a machine should not be fixed by hand and maintained for a long period of time.
I'm only doing it now because it's an experiment.
It's confusing the links for this project, so I'll eventually kick it out to gist or something.
Hopefully, if nothing is done, it will be overwritten after a day and disappear.
Any useful links should be noted on a separate page
(Do we need to be funny about how we do things?)
It's hard to realize, but it's a complete waste of time and effort, because the tedious procedure somehow gives you a sense of doing your job and a mysterious sense of satisfaction.
I noticed that there is also a store in Joynas, Yokohama, and I have been going there about once every two weeks since then.
I realized that I had no motivation to create libraries for devices I didn't use, and I resolved to only create things I would use from then on.
Headless Chrome library was created and got 2000stars by yujiosaka. Eliminate all features that stimulate approval.
I want to eliminate all the elements that would spawn a lackey/administrator within WiKi and have to ask before I edit.
This and the idea of [Eliminate all features that stimulate approval.
I use Scrapbox to eliminate those elements that are obscured by the appearance of real human faces.
Like most editors, I've eliminated switching between edit and view modes because it's only a brake on my thinking, and if there are other toolbars for text decoration, I spend more time fiddling with the font size than writing text.
It is thoroughly eliminated because the time is more and the acceleration is lost.
I especially recommend scrapbox among the wikis because it allows you to write at the speed you think and eliminates the elements that get in the way of your thinking. I think the exchange of opinions should be done on Hatena Diary or Hatena Blog.
dotenv
Can be loaded with require('dotenv').load().
dotenvify
$ browserify -t dotenvify src/index.js -o build/index.js
When .env is missing, dotenv gives warnings It can be suppressed with the silent option, but dotenvify does not have the ability to pass options to dotenv
$ npm i shokai/dotenvify#dotenv-options -save
Version=1; Expires=Tue, 15-Nov-2016 11:51:24 GMT; Max-Age=86400; Domain=staging.scrapbox.io; Path=/; HttpOnly
Version=1; Expires=Tue, 15-Nov-2016 11:51:24 GMT; Max-Age=86400; Domain=staging.scrapbox.io; Path=/; HttpOnly
[Adding ability to specify an agent for OAuth2 requests by PhilipSkinner · Pull Request #324 · ciaranj impressions
It's nice to see other people's presentations on technical keywords that I'm interested in and have written down.
We all think we are using the same Japanese, but there are differences in the choice of words we use to express our thoughts.
In my project, I use the word "exclusion" to refer to the removal of a person from a group of people (this is not my word either, but something I wrote down after seeing other people's expressions).
On the other hand, shokai is used to refer to "removing harmful features or functions from software.
If you look at the keywords displayed and tweak the page in various ways, of course it will be an "updated page" tomorrow, and the same thing will be displayed.
This must be boring.
Remember what you put out once and don't put it out for a week to a month, and so on.
---
This page is auto-translated from /nishio/複数のプロジェクト間のリンクを見つける using DeepL. If you looks something interesting but the auto-translated English is not good enough to understand it, feel free to let me know at @nishio_en. I'm very happy to spread my thought to non-Japanese readers.